1 link tagged with all of: always on agents + agent architecture + event inbox
Click any tag below to further narrow down your results
Links
This guide from Anthropic explains how always-on agents work: they sleep most of the time, wake for short runs triggered by events, and rely on an inbox, timers, memory, permissions, and an outbox to stay coherent across sessions. It's a practical blueprint for teams wanting to make agents proactive without constant supervision.
- An always-on agent runs the same core loop as other agents; the difference is the surrounding architecture that decides when it wakes, what persists between runs, and how output reaches the user.
- Recent model gains in judgment and falling cost per solved task make long-running agents practical; one long-horizon coding benchmark showed Opus 5.5 at 78% lower cost per solved task than Opus 5.
- The event inbox should be a durable store with one active worker per user, deduplicated events, and batching, so crashes don't lose events and competing runs don't collide.